## Introduction

[The Scrum Master](/scrum-roles-3-scrum-master/) role is not easy. It requires **patience** and **curiosity** to learn something new every single day. Being a successful Scrum Master doesn’t mean that you are perfect and don’t make any mistakes. Of course you will make them, but you are also able to learn from them. 

What I will describe today is a process and continuous journey that never ends. You cannot just **become a successful Scrum Master** and then stop doing anything. Be **open-minded** and try to avoid common mistakes that will not serve you. 

## Active Teacher of Scrum

Let’s start from the quote from [Scrum Guide](https://scrumguides.org/scrum-guide.html#scrum-master):

> The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.

Does your team and organisation **know what [Scrum](/blog/first-steps-to-learn-scrum/)** is? Did they read the latest version of the [Scrum Guide](https://scrumguides.org/scrum-guide.html)? 

Successful Scrum Master should be a **teacher** who is able to explain [Scrum](/blog/first-steps-to-learn-scrum/) framework in an **interesting** and **engaging** way. You want to teach [Scrum](/blog/first-steps-to-learn-scrum/) continuously on a daily basis. You really want to make sure that your team and organisation **understand [Scrum](/blog/first-steps-to-learn-scrum/) framework** and they are able to use principles and [Scrum values](/blog/the-importance-of-scrum-values/) in their work. 

### Exercise - Scrum teaching

* Draw the empty version of the **Scrum diagram**. You can use the classic [Scrum.org](https://scrumorg-website-prod.s3.amazonaws.com/drupal/2021-01/Scrumorg-Scrum-Framework-tabloid.pdf) diagram or draw your own version. 

![Scrum-diagram](img/scrum_diagram.png)

* Write all the [Scrum](/blog/first-steps-to-learn-scrum/)**roles, events & artifacts** on sticky notes. 

* Ask the team members to place the **sticky notes** on a diagram and discuss the **most important facts** about the element they put on the board. Allow other attendees for additional insights and thoughts. 

- Don’t correct the **wrong answers straightaway**. Allow the team to help out and correct misunderstandings. Let them self-organize and collaborate as a team. 

*Repeat this exercise **every few months** to build the shared understanding of the [Scrum](/blog/first-steps-to-learn-scrum/) framework and to give the opportunity for clarification. 

## Servant leader not a Scrum Lord

Following the [Scrum Guide](https://scrumguides.org/scrum-guide.html#scrum-master):

>Scrum Masters are true leaders who serve the Scrum Team and the larger organization

Successful Scrum Master should **give the power back to [Developers](/blog/scrum-roles-1-development-team/)** and **trust** that they know how to achieve the [Sprint Goal](/blog/sprint-goal-why-do-we-need-it/). 

One of the really toxic Scrum Master’s antipatterns is becoming a **Scrum Lord** with a **command and control** mentality who assigns tasks and sets deadlines. You don’t want to do that! 

[Developers](/blog/scrum-roles-1-development-team/) should be able to **autonomously** decide how they will work and what serves them well. Even if you don’t agree with their choice, give them the space to experience what they selected. They can use **empiricism** to inspect and adapt if whatever they implemented will not serve them. 

Becoming a successful Scrum Master requires a lot of **self-awareness**. Whenever you try to help your team, ask yourself:

> Am I serving someone else’s needs right now or my own agenda?’

You can use this question as the beginning of **self-retrospection** to analyse what you **can do better to serve others**. 

You can apply the same behaviour when it comes to interactions with [Product Owner](/blog/scrum-roles-2-product-owner/) or stakeholders. Before advising them what they should or shouldn’t do, **listen carefully** and try to understand **what they need**. The best way to serve other people is by addressing their needs and pain points. 

![Leader](img/lead.jpg)

## Quiet Listener and Observer not a Superhero

Are you addicted to the **adrenaline rush** and the **attention** that comes whenever you **solve the problem** for your team? Do you like to **propose solutions** to fix the problems within your Scrum Team? 

If the answer is yes, I must disappoint you. That’s not what a successful Scrum Master does.  When you try to solve problems in your team by yourself, you focus on your personal need to become a **Superhero**, not on **serving the Scrum Team**. 

To be successful in the Scrum Master role you need to **calm down your ego** and be a **quiet listener** who observes what others need.

Does it mean no action? Of course not! You still want to cause the removal of the impediments and facilitate discussions, but it requires **listening** and **observing**. Sometimes it’s better to be quiet to allow people in the room to **express their thoughts and needs.** 

![Silence](img/quiet.jpg)

### Exercise - The Power of Silence 

Whenever you notice that you **talk too much in meetings** e.g. you ask a question and answer it straight away, because people don’t talk, pause for a moment. 

Instead of answering the question by yourself, allow the **power of silence** to do its magic. **Wait for a minute** or even longer if needed. I guarantee you, someone **will finally speak up**, because they will start feeling uncomfortable with silence. 

**Listening and observing** is a powerful mix of skills that will allow you to become a successful Scrum Master. People don’t speak only by words. They show a lot by their **facial expression, tone of the voice or even body posture**. 
Listen & observe others to understand what they need. 

## Facilitator not Scrum Secretary

In many Scrum Teams, Scrum Master acts like a **[Scrum](/blog/first-steps-to-learn-scrum/) Secretary** by updating the statuses, taking notes or even bringing the team coffee. There is nothing wrong in bringing coffee to the team once in a while, but don’t forget what Scrum Master role is about. 

Successful Scrum Master should use **focus** one of the [Scrum Values](/blog/the-importance-of-scrum-values/) to invest time in the most important activities. One of them is not making or bringing coffee, but **facilitating discussions and stakeholders collaboration**. 

As it it mentioned in the [Scrum Guide](https://scrumguides.org/scrum-guide.html#scrum-master) Scrum Master should help the team to focus on:

> creating high-value Increments that meet the Definition of Done.

It requires **asking the right questions** and **challenging the team** whenever it’s needed. Scrum Master needs to keep **coaching the Scrum Team** in self-management and cross-functionality by facilitating discussions and promoting empiricism. 

## Summary

What are the secrets of a successful Scrum Master?

* **Actively teaching** the Scrum Team and organisation how to understand Scrum in theory and in practice. 
* **Serving** instead of a command and control mentality. 
* **Listening and observing** behaviours to understand how to serve and help others instead of being a Superhero.
* **Facilitating and coaching**, not working as a Scrum Secretary. 
What do you think about these secrets? Do you agree with my perspective? If not, what would you change or add?
------------------------------------
#### Sources:
1) Schwaber Ken; Sutherland Jeff. Scrum Guide, https://scrumguides.org/scrum-guide.html. November 2020.
2) Ripley Ryan; Miller Todd. Fixing Your Scrum. Pragmatic Bookshelf. Kindle Edition. January 2020. 

What does it mean to be a successful Scrum Master? What are the behaviours that can help you or stop you from serving others?

Secrets of Successful Scrum Master

## Introduction

In my last 2 posts from Scrum Roles series I explained who is the [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/) and the [Product Owner](https://letsscrumit.com/scrum-roles-2-product-owner/).

Today I would like to tell you more about the role of Scrum Master that is close to my heart, because I act as the Scrum Master in the Scrum Team. 

![Scrum-Master](img/scrummaster.png)

## Who is the Scrum Master?

Before we will start analyzing deeply the role, let’s check what Scrum Guide says about it:

> The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.

The most important responsibility of the Scrum Master role is to help everyone in understanding and using the Scrum framework. This will maximize the value created by the Scrum Team and will help them to build high-performance culture. 

It can sound simple, but there are a lot of skills and actions required from the Scrum Master in order to achieve the above. 

## Scrum Master - servant leader

One of the important things to remember is that: > The Scrum Master is a servant-leader for the Scrum Team. 

It is definitely not the traditional project manager, but the leader who serves the Team and helps them to understand what Scrum is and how they can use it on a daily basis. 
Scrum Master should serve the [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/), [Product Owner](https://letsscrumit.com/scrum-roles-2-product-owner/) and the Organization.  

As a servant leader Scrum Master is responsible for: 
* Removing all impediments during development process 

* Helping to create collaborative and safe culture within the Scrum Team and organization - Finding and proposing new solutions that will help in more efficient development of the product  

* Understanding Scrum Team and organization needs and how they can be fulfilled using an agile approach.

![Servant-Leader](img/servant_leader.jpg)

## Scrum Master - teacher & coach

When I was a young girl, I wanted to become a teacher. What is more, I have even a degree in Early Childhood Education, because teaching others and helping them to grow was always my passion.  After a lot of adventures and changes in my life I become a Scrum Master and I believe that my teaching skills are really useful in this role. 

Scrum Master needs to use coaching skills and teach all below on a daily basis. 

#### Product Owner

*  Clear expression of the business goals, scope and the purpose of the product

* Product Backlog management by finding more effective ways and techniques. This includes making sure that Product Backlog items are clear and understandable for everyone. It should be explained and arranged the way that will maximize the value of the [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/) work. 

* Understand and practice agility and empirical approach in all Scrum activities.

#### Development Team:
* Self-organization and cross- functionality that are crucial part of their growth

* Understand the purpose of the Scrum and practicing it in an agile way on a daily basis

* Create high-value products 

* Resolve conflicts and discuss issues when they appear.

#### The Organization:

* How Scrum can be adopted and what is required from the Organization

* The value of the Scrum in organization and what does it mean to use empirical process in development of the product

* Plan Scrum implementations, cooperate with other Scrum Masters to increase effectiveness in Scrum adoption in organization

* How Organization should interact with the Scrum Team and what will increase the productivity and what won’t.

![Teacher](img/teacher.jpg) 

## Scrum Master - Facilitator

Scrum framework consists of events that increase communication and effectiveness within the team like : [Sprint](https://letsscrumit.com/scrum-events-1-the-sprint/), [Daily Scrum](https://letsscrumit.com/scrum-events-3-daily-scrum/), [Sprint Planning](https://letsscrumit.com/scrum-events-2-sprint-planning/), [Sprint Review](https://letsscrumit.com/scrum-events-4-sprint-review/) and [Sprint Retrospective](https://letsscrumit.com/scrum-events-5-sprint-retrospective/).

Scrum Master needs to facilitate some of these events if it is requested or needed. He or she also needs to make sure that events are organized and the team doesn’t exceed the maximum time dedicated for each event. 

Scrum Master should listen to the team’s discussion and issues they are struggling with and ask the right questions in the right moment.  I would say that one of the most important, but also difficult skills for the Scrum Master is taking the step back and creating space for the [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/) to express their ideas and solutions. 

A lot of Scrum Masters who transformed from the traditional project management approach would like to propose the solution right away instead of giving the freedom to the [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/) to find it by themselves. 

The only way to help the team to be self-organized is to trust them and allow them to make their own decisions and mistakes. This empirical process is the best way to learn and grow. 

![Facilitator](img/facilitator.jpg)

## Summary

* Scrum Master is the role in Scrum Team who **promotes Scrum** and **helps** everyone to **understand** and **practice** it on a daily basis.

* He or she should be the **servant - leader** who supports [Product Owner](https://letsscrumit.com/scrum-roles-2-product-owner/), [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/) and the Organization in their Scrum journey. 

* Scrum Master is responsible for **helping [Product Owner](https://letsscrumit.com/scrum-roles-2-product-owner/) in Product Backlog management** and making sure that everyone in the Scrum Team understands it.

* The [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/) should be **coached** by the Scrum Master how to become a **self-organized and cross-functional team** and deliver the high value products. Scrum Master needs to support them and promote an agile and collaborative approach. 

* Scrum Master has multiple functions such as: **servant-leader, teacher, coach, facilitator** and more depending on what is needed. She or he needs to be the person who adapts to change quickly and helps everyone else to do it. 

Would you like to know who is the Scrum Master? What is her or his role in the Scrum Team?

Scrum Roles #3 Scrum Master

## Introduction

As I mentioned in my last [post](https://letsscrumit.com/scrum-roles-1-development-team/), Scrum Team consists of the [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/), Product Owner and Scrum Master.  I’ve already described the [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/) and today I would like to tell you more about the **Product Owner**. 

## Who is the Product Owner

Let’s check what Scrum Guide says about it: > The Product Owner is one person, not a committee. The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item’s priority must address the Product Owner.

This is important information - Product Owner is **one individual**, not a group of people. Why?  The reason is simple - multiple people mean multiple decisions, visions and increased complexity. 

![Product-Owner](img/productowner.jpeg)

## What is the Product Owner responsible for?

Based on the Scrum Guide:

> The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.

Ok, you may ask now - "What does it mean maximizing value?" 

First of all, a Product Owner needs to have a deep understanding of the product. Based on the knowledge about the product, he or she can decide what direction of the development will be the most valuable. It can be done based on the market situation, company strategy or analysis of the customer needs. As it was described in the Scrum Guide, it can vary across companies. 

The simple example from real life: the Product Owner receives the request from the higher management in the company that they want to implement some additional product functionality urgently. 

Before the Product Owner makes any decisions, he or she needs to analyze all implications related to technical aspects, impediments, customer needs etc.  Based on the analysis the Product Owner decides if the new action will be valuable for the product or not. 

## Product Owner & Product Backlog

As we can read in the Scrum Guide:

> The Product Owner is the sole person responsible for managing the Product Backlog. 

If you don’t know the Scrum yet, you may ask - "What is the Product Backlog?"  It is a list of everything that is required, needed in the product. 
The Product Owner is responsible for creating this list of work items called "Product Backlog items" and managing it. 

![Product-backlog](img/backlog.jpg)

**How can the Product Owner manage the Product Backlog?**
* All Product Backlog items should be clear and understandable for everyone in the Development Team. The most priority items should be fully explained to allow the team to plan their work accordingly.

* Product Backlog should be visible to everyone in the Scrum Team to make sure all requirements and vision of the product are transparent.

* Items need to be ordered by PO based on the business goals and strategy. The most important and priority work should be on the top of the Product Backlog.

* During management of the Product Backlog PO should consider work required from the Development Team and decide how to optimize the value of their work.

Some of the above responsibilities can be done by different people (selected by PO), but the Product Owner remains accountable in terms of the Product Backlog management.

## Product Owner - other responsibilities

The Product Owner is the only person who has authority to cancel the [Sprint](https://letsscrumit.com/scrum-events-1-the-sprint/). It is a really rare case, but this decision can be made by the Product Owner due to technology or market changes.

The Product Owner is also the main link between business and the Development Team. She or he needs to fully understand business needs and clearly express them to the team. 

In Scrum there is one event facilitated mostly by the Product Owner - [Sprint Review](https://letsscrumit.com/scrum-events-4-sprint-review/): 
* All key stakeholders need to be invited by the PO to the meeting. He or she needs to explain what Product Backlog items were "Done" during the Sprint and what is the current status of the Product Backlog.

* Together with all stakeholders and other members of the Scrum Team, the Product Owner analyzes the marketplace, budget and potential timeline.

  
![Stakeholders](img/stakeholders.jpg)

## Product Owner & Sprint Backlog

The Product Owner is responsible for Product Backlog, but what about **Sprint Backlog**?  Sprint Backlog is created during [Sprint Planning](https://letsscrumit.com/scrum-events-2-sprint-planning/) and includes items selected from the Product Backlog for the new [Sprint](https://letsscrumit.com/scrum-events-1-the-sprint/).

The difference between **Product Backlog** and **Sprint Backlog** is that the first one is managed and can be changed by the Product Owner, while the other one belongs solely to the [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/).  It means that the Product Owner cannot update it in the Sprint or add anything. The Development Team can change it and renegotiate selected items with the Product Owner if it’s needed. 

Moreover, the Product Owner plays the important role in **clarification of the Product Backlog Items**. If the Development Team has any concerns related to items selected for the Sprint, the Product Owner should help them and explain all unclear details.

## Summary

To sum up the Product Owner’s role, it is **one person** who makes sure that all the actions within the Sprint are **maximizing value of the product**. 

The Product Owner needs to be the **link between all stakeholders and the Development Team**. She or he should know deeply the product, business needs and marketplace in order to achieve the best results during the product development process. 

The main responsibility of the Product Owner is the **Product Backlog management** including ordering, clarification of items and optimizing the Development Team’s work. 

Who is the Product Owner? What are her or his responsibilities? Read this post to find out more about this Scrum Role.

Scrum Roles #2 Product Owner

## Introdution

Last month, I explained to you in detail all Scrum Events: [Sprint](https://letsscrumit.com/scrum-events-1-the-sprint/), [Sprint Planning](https://letsscrumit.com/scrum-events-2-sprint-planning/), [Daily Scrum](https://letsscrumit.com/scrum-events-3-daily-scrum/), [Sprint Review](https://letsscrumit.com/scrum-events-4-sprint-review/) and [Sprint Retrospective](https://letsscrumit.com/scrum-events-5-sprint-retrospective/).

Today, I would like to start a new series about **Scrum Roles**. You probably think that you can read about Scrum Events and Roles in the Scrum Guide and there is no need to write posts about them. But I believe that practical knowledge and deep explanation of terms used in the Scrum Guide is important to understand the Scrum framework. 

First posts on this blog are written to create the foundation for all interesting discussions about Scrum and Agile. Without solid basics this framework doesn’t work properly.

![Scrum_Team](img/scrumteam.PNG)

## Scrum Team

To explain the Development Team role, I need to start from the broad context.  In the Scrum all roles are part of the Scrum Team.  Based on the Scrum Guide:

> The Scrum Team consists of a **Product Owner**, **the Development Team**, and a **Scrum Master**. Scrum Teams are self-organizing and cross-functional. 

## Self-organizing?

Oh wait! Don’t they need any manager? Yes, that’s right. Self-organizing team doesn’t need to be managed by someone outside the team.  The team knows the best way to organize and accomplish their work. 

## Cross-functional?

What does it mean? It means that together in a team, they have all skills required to do the work. They don’t need to depend on others who are not part of the team. 
To make their work even more effective, the Development Team should aim for spreading the knowledge in the team. It can be achieved by practices like pair programming, learning at lunch events or changing the facilitator on each Scrum Event.
The above attributes of the Scrum Team increase productivity and flexibility of the team. What is more, Scrum Team inspired by their own autonomy is more creative and delivering complex products is much easier for them. 


## Who is part of the Development Team?

Great, we know that the Development Team is one of the roles in the Scrum Team.  Let’s check in the Scrum Guide who is part of the Development Team:

> The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of "Done" product at the end of each Sprint.

In the Development Team you can find everyone who gets product development work done. I will list examples from software development, but remember that Scrum can be used in any other industry. 

If we develop software products, Development Team can consists experts in:
* Software Engineering
* Designing
* Testing
* Software Architecture
* Business Analysis
* And everything else what is required to get things done.

![Development_Team](img/developmentteam.PNG)

## What is the size of the Development Team?

Based on the Scrum Guide:

> Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint.

Size of the Development Team should be from **3 to 9 people**. Smaller teams will be less productive and they can struggle with delivering the increment. On the other hand, a bigger team increases complexity what can cause communication and collaboration issues. 
Scrum Master and Product Owner are not part of the Development Team unless they also do the work from the Sprint Backlog.

## What are the atributes of the Development Team

The Development Team as a part of the Scrum Team needs to be **self-organized** and **cross-functional**.  They decide what is included in the Sprint Backlog and how they will achieve the [Sprint Goal](https://letsscrumit.com/sprint-goal-why-do-we-need-it/) that they planned.

The most important for the team is **delivery of the releasable increment of "Done"** product at the end of each Sprint. They create the definition of "Done" and decide how it will be verified. 

The Development Team should **consist of people with the right skills** to be able to effectively organize their own work and deliver the product increment.
 
Based on the Scrum Guide:
> Individual Development Team members may have specialized skills and areas of focus, but **accountability belongs to the Development Team as a whole**.

It is crucial for the team to remember about and support each other and collaborate effectively in order to achieve their goals.

![Attributes](img/attributes.jpg)

## Titles and sub-teams in the Development Team

Based on the Scrum Guide:
> - Scrum recognizes no titles for Development Team members, regardless of the work being performed by the person
> - Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to be addressed like testing, architecture, operations, or business analysis

**What does it mean in reality?**

It means that the Development Team should work together without anything like titles or sub-team what could divide them.  During [Sprint Planning](https://letsscrumit.com/scrum-events-2-sprint-planning/) they need to estimate work considering all skills and knowledge in the team.  If there are less experienced people in the team, others should teach them and help to develop all necessary skills. 

## Responsibilities of Development Team

What is the Development Team Responsible for? 
* Getting things **Done**

* Development of releasable **increment** of product

* **Planning** their work on the [Sprint Planning meeting](https://letsscrumit.com/scrum-events-2-sprint-planning/)

* **Sprint Backlog** - it can be adjusted after agreement between Development Team and Product Owner

* Achievement of the [Sprint Goal](https://letsscrumit.com/sprint-goal-why-do-we-need-it/) planned for the Sprint

* Managing their work daily, planning and **inspection** during [Daily Scrum](https://letsscrumit.com/scrum-events-3-daily-scrum/)

* Demonstration of **"Done"** work during [Sprint Review](https://letsscrumit.com/scrum-events-4-sprint-review/)

* **Analyzing** their work, relationships and processes during [Sprint Retrospective](https://letsscrumit.com/scrum-events-5-sprint-retrospective/). They need to inspect and adapt if needed

* **Continues improvement** of their work and processes.

![Responsibilities](img/responsibilities.jpg)

## Summary 

To summarize, the Development Team is responsible for **"Done"** work in the Sprint and "How" it will be done. As a **self-organizing** and **cross-functional** team, they find the best solutions to deliver the product effectively. They **inspect** their work and **adapt** to achieve better results, but also to increase creativity in the team. 

They need to be **transparent** in all their actions to build **trust** and **respect** in the team and create a safe environment for every team member.

Would you like to know who is in the Development Team and what are respnsibilities of the team? Check out this post to find out more.

4 posts tagged with #scrum roles